home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 2
/
The Arsenal Files 2 (Arsenal Computer).ISO
/
dbase
/
btriev.txt
< prev
next >
Wrap
Text File
|
1994-04-23
|
6KB
|
132 lines
Btrieve parameters
------------------
BTRIEVE [/M:xx] Memory size
[/P:xx] Page size
[/T:xx] Transaction filename
[/C] Index compaction
[/U:xx] Compression buffer size
[/I:xx] Pre-image file drive
[/B:xx] Pre-image buffer size
[/F:xx] Open files
[/L:xx] Locks
[/E] Expanded memory
[/O] Override critical error
/M:xx Memory size
-----------------
The memory size option determines the memory size in kilobytes units
of Btrieve's cache buffers. The default value for this option is 32KB.
Valid sizes are from 9KB to 64KB inclusive.
ex. /M:48
/P:xx Page size
---------------
The page size option specifies the maximum page size of any Btrieve
file you wish to access. This option, along with the /M option,
determines the size of buffers Btrieve allocates in cache. When
you omit the /P option, Btrieve calculates a buffer size based on the
amount of memory you specified with the /M option.
The page size you specify must be a multiple of 512 bytes but can be
no greater than 4096 bytes. If you specify a page size of 4096 bytes,
you must specify at least 36KB for the /M option. The larger the page
size, the fewer buffers Btrieve allocates within the memory specified
on the /M option.
ex. /P:1536
/T:xx Transaction filename
--------------------------
The transaction filename option specifies the location where you
want Btrieve to store the transaction control file. You must specify
the transaction filename option if your application issuses Begin,
End, or Abort Transaction calls. The filename may include a drive
and directory specification.
ex. /T:C:\CLARION3\CLARION3.TRN
/I:xx Pre-image file-drive
--------------------------
The pre-image file drive option directs your pre-image files to a
drive other than the one storing Btrieve files. If the drive you specify
is a RAM disk, the disk I/O normaly required for pre-imaging is
eliminated, but Btrieve cannot automatically recover damaged files
after a system failure. If one station on the network loads Btrieve
with the /I option, all stations should do so.
ex. /I:D
/C Index compaction
-------------------
The index compaction option directs Btrieve to perform index
compaction on update and insert operations.
ex. /C
/B:xx Pre-image buffer-size
---------------------------
The pre-image buffer size option specifies the total amount of memory
Btrieve uses for pre-image buffers. The default value is 16KB.
ex. /B:5
/F:xx Open files
----------------
The open files option specifies the maximum number of unique
Btrieve data files an application can have open simultaneously in the
system. The default value is 20. The maximum number you can specify
is 255.
ex. /F:128
/L:xx Locks
-----------
The locks option specifies the maximum number of multiple record
locks that can be active simultaneously at a workstation. Specifically
this option determines the number of antries for the lock table that
Btrieve builds when it loads.
The default value for the /L option is 20. The maximum value you can
specify for this option is 255. Each lock increases the memory resident
size of Btrieve by six bytes.
ex. /L:40
/E Expanded memory
------------------
The expanded memory option does not require an argument. When
you specify the /E option, Btrieve will not use expanded memory for
its data buffers. You do not need to specify the /E option if your
machine does not use expanded memory. Btrieve checks for the
presence of expanded memory when it loads, and uses the main
memory of the computer if no expanded memory is present.
If your application stores its data in expanded memory, you must
specify the /E option when you load Btrieve. Data stored in
in Btrieve's data segment can be corrupted if both Btrieve and your
application store data in expanded memory. Btrieve will not return
an error in this situation.
ex. /E
/O Override critical error
--------------------------
The override critical error option controls the way Btrieve responds
to a DOS critical error, such as "Drive Not Ready". The /O option does
not require an argument.
If you do NOT specify the /O option when you start Btrieve, it will
route the error to the standard DOS critical error handler. This
usually result in a DOS error message being written to the screen. The
user can either abort or retry the operation in response to the error.
If you specify the /O option and a DOS critical error occurs during a
Btrieve disk operation, Btrieve will return a status code, usually a
status 2 (I/O error) or 12 (File not found), to your application
ex. /O
/U:xx Compression buffer size
-----------------------------
Btrieve uses the compression buffer size option to allocate the length
of the compression buffer it uses for data compression and expansion.
If your application does not use compressed files, do not include this
option when you start Btrieve. If your application accesses compressed
Btrieve files, you must specify a value for the /U option when you start
Btrieve.
The value you specify must be at least equal to the length of the
largest record your application reads from or writes to a compressed
Btrieve file. If your application updates records, the buffer size you
specify with the /U option must be large enough to hold the largest
expanded record. Always specify the value for the /U start-up option
in KB. Btrieve will allocate twice the amount of memory you specify
to the compression buffer.
Round any uneven value up to the next higher kilobyte value.
ex. /U:2